fix: added pending callbacks mechanism to solve npe crash #332
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Solves this issue:
Crash Log
It is easily reproducible with example app in react-native-geolcation repo.
Reproducer App: https://github.com/michalchudziak/react-native-geolocation/tree/master/example
Steps to repro:
Issue Summary
The mSingleLocationCallback gets overwritten when multiple calls to getCurrentPosition() are made before the previous call finishes. This leads to a situation where null is passed to mFusedLocationClient.removeLocationUpdates(), causing the Listener must not be null exception.
Changes Made:
getCurrentLocationData
,startObserving
, andstopObserving
methods to handle the addition and removal of callbacks more safely and consistently.Test Plan
Tested
getCurrentPosition
andwatchPosition
functionality.